Your organization already has defaults. Do you know what they are?
Most organizations have strategies, values, goals, and nice-looking slide decks about how work should happen.
But then there is the other layer.
The real layer.
The meetings that happen every week because they have always happened. The decisions that somehow always end up with the same few people. The tools that quietly decide what gets attention. The Slack messages that become the unofficial prioritization system. The onboarding that teaches people the formal process, while the actual process is learned by watching what others do.
These are organizational defaults.
They are the settings that shape how work happens when no one is actively designing it.
And the interesting thing is: every organization has them.
Defaults are not always bad
When I talk about defaults, I do not mean that everything hidden or automatic is a problem. Some defaults are useful. They reduce cognitive load. They help people know what to do without asking every time. They make collaboration easier.
A good default might be:
decisions are documented clearly
meetings have a clear owner and purpose
new people know where to find information
teams have shared language for priorities
feedback is part of the work, not a separate event
These kinds of defaults make good work easier.
The problem starts when the default setting supports something the organization does not actually want.
For example, a company might say it values focus, but the default is constant meetings and instant replies. It might say it values ownership, but decision rights are unclear. It might say it values learning, but people only get feedback when something goes wrong.
This is where the gap appears between intention and reality.
What are your ways of working optimizing for?
One of the most useful questions an organization can ask is:
What are our current ways of working already optimizing for?
Not what we hope they optimize for. Not what the strategy says. But what they actually make easier in everyday work.
Do they make it easier to focus, or easier to react?
Do they make it easier to collaborate, or easier to avoid difficult conversations?
Do they make it easier to take ownership, or easier to escalate everything upward?
Do they make it easier to learn, or easier to repeat the same patterns?
This is where organizational defaults become visible. They show up in routines, tools, incentives, roles, communication habits, and decision-making patterns.
Often, people have already noticed these things. They just may not have had the language for them.
Someone might say, “We always end up discussing the same issue again.”
Or, “Nobody really knows who owns this.”
Or, “We say this is important, but it never gets time.”
Or, “The process exists, but no one uses it.”
These are not just small frustrations. They are signals.
They tell us something about how the system is currently designed.
Recognizing defaults is the first step to changing them
In my work, I am interested in helping organizations notice these patterns before jumping into solutions.
Because it is tempting to start with a new tool, a new process, a new operating model, or a new meeting structure. Sometimes those are needed. But if we do not first understand the current defaults, we may only add another layer of complexity on top of what already exists.
A designed defaults review asks questions like:
What does the current setup make easy?
What does it make difficult?
What behaviors does it reward?
What gets attention?
What gets ignored?
Where do people need to compensate for unclear structures?
Where are people asked to “try harder” when the system itself needs redesigning?
These questions are not about blaming people. Usually, people are doing their best within the environment around them.
The point is to understand the environment.
Because once we can see the defaults, we can start designing better ones.
Better defaults make better work easier
The goal is not to create a perfect organization. That does not exist.
The goal is to create conditions where the desired way of working becomes easier, more visible, and more natural.
If responsibility matters, it needs to show up in decision-making.
If wellbeing matters, it needs to show up in workload and prioritization.
If learning matters, it needs to show up in feedback loops.
If strategy matters, it needs to show up in what teams actually spend time on.
That is the practical work of organizational development: not only defining where we want to go, but understanding what currently guides people’s behavior, and redesigning the defaults that shape everyday work.
Because culture is not only what we say.
It is also what the system makes easy.
